This PR adds PROBE_RESET_SCORES support to the mainnet probe spec, so each run can start from a fresh pathfinding scorer.

Description

• When PROBE_RESET_SCORES=true (default false), the probe spec calls the new resetScores devtools method after wallet restore and before readiness: the app stops the node, deletes the scorer and external_pathfinding_scores_cache VSS keys, and restarts the node
• Readiness is then additionally gated on the scores sync: the node's latestPathfindingScoresSyncTimestamp must be at most PROBE_SCORES_SYNC_MAX_AGE_S (default 900s) old and newer than the reset start time, guarding against a failed external scores fetch silently producing a "no scores" run (the sync timestamp persisted in node metrics survives the restart)
• Adds scoresSync to the readiness summary and Scores reset to the probe report
• Documents PROBE_RESET_SCORES, PROBE_RESET_SCORES_TIMEOUT_SECONDS, PROBE_SCORES_SYNC_MAX_AGE_S, and PROBE_RESET_SCORES_METHOD in docs/mainnet-probe.md

Without the reset, locally learned scores accumulate in VSS under the probe seed across runs (probe results train the scorer), so consecutive scorer A/B runs are not comparable.

Pairs with:

• feat: add resetScores devtools command bitkit-android#1005
• synonymdev/bitkit-nightly#24

QA Notes

Manual Tests

• 1. Local run with PROBE_RESET_SCORES=true against a mainnet e2e APK: reset completes (~7s), readiness satisfied with fresh scoresSync timestamp, probes run.
• 2. regression: run without PROBE_RESET_SCORES: behavior unchanged (no reset, no scores sync gating).

Automated Checks

• Typecheck passes for the changed files (remaining errors are pre-existing unused imports in unrelated specs).
• Device logs verified the full reset sequence: VSS deletes confirmed by server, node rebuilt without cache merge, fresh external scores downloaded post-reset.

Made with Cursor